Tactile input device for a touch screen

ABSTRACT

Systems, methods, and apparatuses for tactile user input are described herein. A tactile user input system includes a tactile input device and a smart table. The smart table comprises a network interface and a processing circuit. The processing circuit comprises a processor and a memory. The processing circuit is structured to sense a placement of the tactile input device on the smart table. The processing circuit is further structured to determine a necessary user input and determine a location of the tactile input device on the smart table. The processing circuit is further structured to rearrange a user interface of the smart table. The processing circuit is further structured to communicate a necessary input configuration to the tactile input device and used by the tactile input device to generate a tactile user interface having an appropriate layout based on the necessary input configuration.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of U.S. patent applicationSer. No. 17/079,971 filed Oct. 26, 2020, a continuation-in-part of U.S.patent application Ser. No. 17/079,961 filed Oct. 26, 2020, and acontinuation-in-part of U.S. patent application Ser. No. 17/079,958filed Oct. 26, 2020, each of which are incorporated herein by referencein their entirety.

TECHNICAL FIELD

This application relates generally to the use of a smart table toimprove efficiency and ease of conducting transactions at a providerlocation associated with a provider. More specifically, this applicationrelates to systems and methods for providing tactile input on a touchscreen, including the use of a tactile input device.

BACKGROUND

Customers of a provider are able to access a variety of services throughapplications, such as mobile applications on user devices, to performvarious tasks. For example, customers may use an internet enabledapplication to conduct transactions, change settings, and carry outother actions related to a customer account or with respect to a productoffered by the provider. However, certain transactions and tasks mayrequire a customer to visit a provider location (e.g., due to security,needing to meet with a provider representative) where inputs arerequired to be made by the user on hardware at the provide location,such as on a touchscreen interface with which the user is notaccustomed.

SUMMARY

One example embodiment relates to a tactile user input system associatedwith a provider. The tactile user input system comprises a tactile inputdevice and a smart table. The smart table comprises a network interfaceand a processing circuit. The network interface is structured tofacilitate data communication with the tactile input device via anetwork. The processing circuit comprises a processor and a memory. Theprocessing circuit is structured to sense a placement of the tactileinput device on the smart table. The processing circuit is furtherstructured to determine a necessary user input. The processing circuitis further structured to determine a location of the tactile inputdevice on the smart table. The processing circuit is further structuredto rearrange a user interface of the smart table based on at least oneof the necessary user input or the location of the tactile input deviceon the smart table. The processing circuit is further structured tocommunicate a necessary input configuration to tactile input device tobe used by the tactile input device to generate a tactile user interfacehaving an appropriate layout based on the necessary input configuration.

Another example embodiment relates to a tactile input device. Thetactile input device comprises a touch screen and a tactile overlay. Thetactile overlay including a plurality of selectively inflatable keysconfigured to selectively generate a plurality of tactile userinterfaces, each of the plurality of tactile user interfaces having aunique layout. The tactile input device further comprises at least oneprocessing circuit configured to receive a necessary input configurationfrom a smart table. The processing circuit is further configured togenerate a tactile user interface having an appropriate layout based onthe necessary input configuration. The processing circuit is furtherconfigured to receive, by the touch screen, a user input. The processingcircuit is further configured to communicate the user input to the smarttable.

Another example embodiment relates to a tactile input device. Thetactile input device comprises a tactile overlay including a pluralityof selectively inflatable keys. The tactile overlay is configured toselectively generate a plurality of tactile user interfaces. Each of theplurality of tactile user interfaces has a unique layout and at leastone processing circuit. The at least one processing circuit isconfigured to receive a necessary input configuration from a smarttable. The processing circuit is further configured to generate atactile user interface having an appropriate layout based on thenecessary input configuration.

These and other features, together with the organization and manner ofoperation thereof, will become apparent from the following detaileddescription when taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a smart table system including a providercomputing system and a smart table, according to example embodiments.

FIG. 2 is a block diagram of the smart table of FIG. 1, according toexample embodiments.

FIG. 3 is a flow diagram of a method for initiating a session with thesmart table of FIG. 1, according to example embodiments.

FIG. 4 is an illustration of various configurations of the smart tableof FIG. 1, according to example embodiments.

FIG. 5 is an illustration of additional configurations of the smarttable of FIG. 1, according to example embodiments.

FIG. 6 is an illustration of a user interface of the smart table andpaired user devices of FIG. 1, according to example embodiments.

FIG. 7 is an illustration of a user interface of the smart table of FIG.1 configured to receive an input from a customer or providerrepresentative, according to example embodiments.

FIG. 8 is an illustration of the smart table of FIG. 1 including adispensing mechanism, according to example embodiments.

FIG. 9 is an illustration of various user interface orientationsdisplayable by the smart table of FIG. 1, according to exampleembodiments.

FIG. 10 is an illustration of example user interfaces of the user deviceof FIG. 1 when the user device is paired to the smart table of FIG. 1,according to example embodiments.

FIG. 11 is a block diagram of the tactile input device of FIG. 1,according to example embodiments.

FIG. 12 is an illustration of a tactile input device on the smart tableof FIG. 1, according to example embodiments.

FIG. 13 is an illustration of a side view of the tactile input device,according to example embodiments.

FIG. 14 is an illustration of the tactile input device configured in aQWERTY keyboard layout, according to example embodiments.

FIG. 15 is an illustration of the tactile input device configured in anumeric keypad layout, according to example embodiments.

FIG. 16 is an illustration of the tactile input device configured in anauthorization layout, according to example embodiments.

FIG. 17 is an illustration of the tactile input device configured in asignature box layout, according to example embodiments.

FIG. 18 is an illustration of the tactile input device configured tomeasure the weight of a safety deposit box, according to an exampleembodiment.

FIG. 19 is a flow diagram of a method for utilizing the tactile inputdevice for user input to the smart table of FIG. 1, according to anexample embodiment.

DETAILED DESCRIPTION

Referring generally to the figures, apparatuses, systems and methods fora tactile input device are shown and described. The apparatuses, systemsand methods described herein enhance the input of information to a smarttable by utilizing a tactile input device that allows for more efficientinput and the ability to enter more types of information than can beinput in the smart table alone.

For example, the tactile input allows for the user to input informationmore efficiently. This is achieved by providing a tactile overlay thatprovides the user a tactile reference for the location of keys. Thisallows the user to more efficiently enter information as they are ableto enter information without the necessity of looking at their fingerswhen typing. The tactile input device further improves the functioningof a smart table by allowing for an encrypted separation between theinput device and the smart table. Further, the tactile input deviceallows for the determination of the weight of a desired item (e.g.,safety deposit box, currency).

The embodiments of the tactile user input system described hereinimprove current user input systems by providing the ability to modify asingle user input device to allow for a multitude of different layouts(e.g., alphanumeric, numeric, signature box, weight measurement). Thisimproves efficiency and enhances the functioning of a computer, as thesmart table doesn't need to connect to a multitude of different inputdevices. Additionally, the tactile input device may be configured tochange the layout dependent on the step in the banking session, or afield of focus. This ability may also increase the efficiency ofinformation entry as well as the functioning of the computer, asmultiple input devices are not needed.

Further, the embodiments of the tactile user input system describedherein improve current user input systems by allowing the bankingsession to be completed, at least partially, by the tactile inputdevice. For example, the customer may be provided with the tactile inputdevice and be able enter general information while waiting for a smarttable to become available. Additionally, the tactile input device mayallow for a single tactile input device to be used and transferredbetween a branch employee and a customer through the banking session.Further, the tactile input device may improve the efficiency of abanking session by allowing a user to continue a banking sessionremotely to the smart table. For example, a branch employee may be ableto take the tactile input device to a manager of a branch employee forapproval or authorization, then continue the banking session on thesmart table.

Before turning to the figures, which illustrate certain exemplaryembodiments in detail, it should be understood that the apparatuses,systems and methods for a tactile input devices described herein are notlimited to the details or methodology set forth in the description orillustrated in the figures. It should also be understood that theterminology used herein is for the purpose of description only andshould not be regarded as limiting.

Referring to FIG. 1, a block diagram of a smart table system 100 isshown, according to example embodiments. The smart table system 100includes a provider computing system 102 associated with a provider,such as a service provider, bank, or financial institution. The smarttable system 100 further includes one or more user devices (e.g., userdevice 104), one or more smart tables (e.g., smart table 106), and abranch computing system 108 (e.g., a computing system of a branchlocation of the FI). In some embodiments, the provider computing system102, user device 104 (as well as any additional user devices), smarttable 106 (and any additional smart tables), and branch computing system108 are directly communicably coupled. In some embodiments, thecomponents of smart table system 100 may be communicably and operativelycoupled to each other over a network, such as network 154, that permitsthe direct or indirect exchange of data, values, instructions, messages,and the like (represented by the double-headed arrows in FIG. 1). Thenetwork 154 may include one or more of a cellular network, the Internet,Wi-Fi™, Wi-Max™, a proprietary banking network, a proprietary retail orservice provider network, and/or any other kind of wireless or wirednetwork.

Each system or device in smart table system 100 may include one or moreprocessors, memories, network interfaces and user interfaces. The memorymay store programming logic that, when executed by the processor,controls the operation of the corresponding computing system or device.The memory may also store data in databases. For example, memory 142 maystore programming logic that when executed by processor 140 withinprocessing circuit 138, causes employee database 144 to updateinformation for an employee account with communications received from auser device 104. The network interfaces (e.g., network interface 110 ofprovider computing system 102) may allow the computing systems anddevices to communicate wirelessly or otherwise. The various componentsof devices in smart table system 100 may be implemented via hardware(e.g., circuitry), software (e.g., executable code), or any combinationthereof. Devices and components in FIG. 1 can be added, deleted,integrated, separated, and/or rearranged in various embodiments of thedisclosure.

The provider computing system 102 may be managed by a provider, such asa credit card issuer, a bank, a retailer, a service provider, and/or thelike. The provider computing system 102 includes a network interface110, a processing circuit 112, and an input/output device 122. Thenetwork interface 110 is structured and used to establish connectionswith other computing systems and devices (e.g., the user devices 104,the smart tables 106, the branch computing system 108, etc.) via thenetwork 154. The network interface 110 includes program logic thatfacilitates connection of the provider computing system 102 to thenetwork 154. For example, the network interface 110 may include anycombination of a wireless network transceiver (e.g., a cellular modem, aBluetooth™ transceiver, a WiFi™ transceiver, etc.) and/or a wirednetwork transceiver (e.g., an Ethernet transceiver). In somearrangements, the network interface 110 includes the hardware andmachine-readable media sufficient to support communication over multiplechannels of data communication. Further, in some arrangements, thenetwork interface 110 includes cryptography capabilities to establish asecure or relatively secure communication session in which datacommunicated over the session is encrypted.

The processing circuit 112 includes a processor 114, a memory 116, and aprovider client application 120. The memory 116 may be one or moredevices (e.g., RAM, ROM, Flash memory, hard disk storage) for storingdata and/or computer code for completing and/or facilitating the variousprocesses described herein. The memory 116 may be or includenon-transient volatile memory, non-volatile memory, and non-transitorycomputer storage media. Memory 116 may include database components,object code components, script components, or any other type ofinformation structure for supporting the various activities andinformation structures described herein. Memory 116 may be communicablycoupled to the processor 114 and include computer code or instructionsfor executing one or more processes described herein. The processor 114may be implemented as one or more application specific integratedcircuits (ASICs), field programmable gate arrays (FPGAs), a group ofprocessing components, or other suitable electronic processingcomponents. As such, the provider computing system 102 is configured torun a variety of application programs and store associated data in adatabase of the memory 116. One such application may be the providerclient application 120.

The memory 116 may store a customer account database 118, according tosome embodiments. The customer account database 118 may be configured tostore updated personal information for customer accounts associated withthe provider (e.g., the FI). For example, the customer account database118 saves personal user information, such as name, age, gender, address,education, occupation, etc., customer preferences, such as notificationpreferences, security preferences, etc., and authentication information,such as customer passwords, biometric data for the customer, etc. Insome embodiments, the customer account database 118 includes a tokenvault that stores an associated customer token and/or device token foreach customer account. The customer account database 118 may further beconfigured to store financial data for each customer account, such aspast transactions, different banking account information (e.g.,balances, debt, type of account, etc.), investments, loans, mortgages,and so on.

In some embodiments, the provider client application 120 may beincorporated with an existing application in use by the providercomputing system 102 (e.g., a mobile banking application, a serviceprovider application, etc.). In other embodiments, the provider clientapplication 120 is a separate software application implemented on theprovider computing system 102. The provider client application 120 maybe downloaded by the provider computing system 102 prior to its usage,hard coded into the memory 116 of the provider computing system 102, orbe a network-based or web-based interface application such that theprovider computing system 102 may provide a web browser to access theapplication, which may be executed remotely from the provider computingsystem 102. Accordingly, the provider computing system 102 may includesoftware and/or hardware capable of implementing a network-based orweb-based application. For example, in some instances, the providerclient application 120 includes software such as HTML, XML, WML, SGML,PHP (Hypertext Preprocessor), CGI, and like languages.

In the latter instance, a user (e.g., a provider employee) may have tolog onto or access the web-based interface before usage of theapplication. In this regard, the provider client application 120 may besupported by a separate computing system including one or more servers,processors, network interface, and so on, that transmit applications foruse to the provider computing system 102.

In certain embodiments, the provider client application 120 includes anapplication programming interface (API) and/or a software developmentkit (SDK) that facilitate the integration of other applications with theprovider client application 120. For example, the provider clientapplication 120 is configured to utilize the functionality of the branchcomputing system 108 by interacting with the branch client application150 through an API.

Still referring to FIG. 1, the input/output device 122 is structured toreceive communications from and provide communications to provideremployees associated with the provider computing system 102. Theinput/output device 122 is structured to exchange data, communications,instructions, etc. with an input/output component of the providercomputing system 102. In one embodiment, the input/output device 122includes communication circuitry for facilitating the exchange of data,values, messages, and the like between the input/output device 122 andthe components of the provider computing system 102. In yet anotherembodiment, the input/output device 122 includes machine-readable mediafor facilitating the exchange of information between the input/outputdevice and the components of the provider computing system 102. In yetanother embodiment, the input/output device 122 includes any combinationof hardware components, communication circuitry, and machine-readablemedia.

In some embodiments, the input/output device 122 includes suitableinput/output ports and/or uses an interconnect bus (not shown) forinterconnection with a local display (e.g., a touchscreen display)and/or keyboard/mouse devices (when applicable), or the like, serving asa local user interface for programming and/or data entry, retrieval, orother user interaction purposes. As such, the input/output device 122may provide an interface for the user to interact with variousapplications (e.g., the provider client application 120) stored on theprovider computing system 102. For example, the input/output device 122includes a keyboard, a keypad, a mouse, joystick, a touch screen, amicrophone, and the like. As another example, input/output device 122,may include, but is not limited to, a television monitor, a computermonitor, a printer, a facsimile, a speaker, and so on.

The branch computing system 108 similarly includes a network interface136, a processing circuit 138, and an input/output device 152. Thenetwork interface 136, the processing circuit 138, and the input/outputdevice 152 may function substantially similar to and include the same orsimilar components as the components of provider computing system 102,such as the network interface 110, the processing circuit 112, and theinput/output device 122, described above. As such, it should beunderstood that the description of the network interface 110, theprocessing circuit 112, and the input/output device 122 of the providercomputing system 102 provided above may be similarly applied to thenetwork interface 136, the processing circuit 138, and the input/outputdevice 152 of the branch computing system 108.

For example, the network interface 136 is similarly structured and usedto establish connections with other computing systems (e.g., theprovider computing system 102, the user devices 104, and/or the smarttables 106) via the network 154. The network interface 136 may furtherinclude any or all of the components discussed above, with reference tothe network interface 110.

The processing circuit 138 similarly includes a processor 140 and amemory 142. The processor 140 and the memory 142 are substantiallysimilar to the processor 114 and the memory 116 described above, withreference to the provider computing system 102. In some embodiments, thememory 142 includes an employee database 144 and a smart table database146. The employee database 144 may be structured to store dataconcerning each employee associated with the branch location. In someembodiments, the employee database 144 may store data regarding anidentification number, a job position, authorization information,contact information, a schedule, customer history, work history, anassociated user device 104, credentials, and so forth, of an employeethat works at the branch location associated with the branch computingsystem 108. For example, the employee database 144 may save biometricinformation (e.g., a fingerprint scan, an eye scan, a voice memo, etc.)and a password (e.g., PIN, alphanumeric code, QR code, barcode, etc.)for each employee at the branch location. As another example, theemployee database 144 stores security and data access rights for eachemployee that are utilized in conducting particular transactions(high-risk transactions, transactions with high-confidentialitycustomers, etc.).

Additionally, the employee database 144 may include the types oftrainings each employee has received, the clearances that each employeehas obtained, a trustworthiness score for each employee, and any otherpertinent information pertaining to each employee that may be used todetermine the employees qualifications for performing varioustransactions and other tasks using a smart table 106.

The smart table database 146 may be structured to store data for eachsmart table 106 at the branch location. The smart table database 146 maysave information regarding an identification number of each smart table106, service history information (e.g., a last date a smart table wasserviced for repairs and/or updates), transaction history information(e.g., number of customers that used the smart table 106), schedulinginformation (e.g., customers assigned to the smart table 106 for anupcoming smart table banking session, and/or power status (e.g.,charging, operating on a low battery level, etc.). For example, thesmart table database 146 may store a schedule of which customers will beusing a particular smart table 106 at the branch location. Beneficially,this may allow for branch managers to more effectively plan out smarttable banking sessions and decrease the likelihood of schedulingconflicts, such as two customers having conflicting sessions at the samesmart table 106.

The processing circuit 138 also is shown to include a smart tablemanagement circuit 148. In some embodiments, the smart table managementcircuit 148 is configured to receive new data (e.g., from the network154) relating to employees and smart tables 106 at a branch location.The smart table management circuit 148 may then update a correct,corresponding database (e.g., employee database 144 or smart tabledatabase 146). In some embodiments, the smart table management circuit148 is configured to receive requests from customers for an appointmentat a smart table 106. The smart table management circuit 148 may thenschedule the appointment based on what the client wants to accomplishduring the banking session (e.g., to ensure the assigned smart table 106has the necessary capabilities, such as a functional cash dispenser) andthe available smart tables 106 during a time slot desired by thecustomer.

The smart table management circuit 148 may also be configured toidentify which employees may be needed at a smart table 106 in order toconduct a planned transaction with a customer during a banking session.For example, in generating a request for a smart table banking session,a customer may be asked (e.g., via the user device 104 associated withthe customer) what type of transaction or banking task does the customerwant to complete during the smart table session. In some embodiments,the smart table management circuit 148 may generate and transmit anotification to user device 104 of an employee that a new smart tablebanking session, assigned to the employee, has been scheduled.

Although the employee database 144, smart table database 146, and smarttable management circuit 148 are shown as being a part of the branchcomputing system 108, these components may alternatively be a part ofthe provider computing system 102. In other embodiments, each of theprovider computing system 102 and the branch computing system 108 mayinclude a corresponding smart table management circuit the same as orsimilar to the smart table management circuit 148.

The branch computing system 108 is similarly structured as the providercomputing system 102 to run a variety of application programs and storeassociated data in a database of the memory 142. One such applicationmay be the branch client application 150, for example.

The branch client application 150 may be substantially similar to theprovider client application 120, but may instead be tailored towardbranch employees or a branch manager at the branch location. Forexample, branch client application 150 is structured to generate userinterfaces to display on a smart table 106 to facilitate improvedcustomer experiences and employee interactions during an establishedbanking session. Particularly, the branch client application 150 isconfigured to communicate with the provider computing system 102, theuser devices 104 (e.g., customer user devices and employee userdevices), and smart tables 106 to receive instructions or documents fromthe provider computing system 102 and/or the branch computing system 108to complete specific tasks during a banking session at a smart table106. Furthermore, the branch client application 150 may be configured tocommunicate reminders to user devices 104 of employees regardingupcoming banking sessions at a smart table 106 and/or ongoing bankingsessions at a smart table 106 to perform a task associated with thebanking session. For example, the branch client application 150 may beconfigured to generate a reminder for a branch employee to prepare asmart table 106 for an upcoming banking session. Accordingly, the branchclient application 150 is communicably coupled to the provider computingsystem 102 (e.g., through interactions with the provider clientapplication 120), the user devices 104 (e.g., through interactions withthe user client application 132), and the smart tables 106 (e.g.,through interactions with the smart table client application 218 (FIG.2)).

The branch client application 150 may thus communicate with the providercomputing system 102, the user devise 104, and the smart tables 106 toperform a variety of functions. For example, the branch clientapplication 150 is configured to reset a display of a smart table 106(e.g., reset a display to a generic welcome display or sleep modedisplay) at the end of a banking session with a customer. As such, thebranch client application 150 allows for a branch manager and branchemployees associated with the branch location to monitor and update userinterfaces of the smart tables 106 before, during, and after bankingsessions with one or more customers paired to one of the smart tables106.

The input/output device 152 may function substantially similarly to andinclude the same or similar components as the input/output device 122described above, with reference to the provider computing system 102.Accordingly, it will be understood that the description of theinput/output device 122 described above may also be applied to theinput/output device 152 of the branch computing system 108. As anexample, the input/output device 152 is similarly structured to receivecommunications from and provide communications to user devices 104 ofbranch employees and/or the branch manager associated with the branchcomputing system 108.

The smart table system 100 also includes one or more user devices 104,according to some embodiments. The user devices 104 may be a variety ofsuitable user computing devices. For example, the user devices 104 maycomprise mobile phones. In other embodiments, the user devices 104include personal computers (e.g., desktop computers or laptopcomputers), tablets, smart watches or other wearable devices,headphones, smart vehicle voice/touch command systems, virtual/augmentedreality (VR/AR) systems (e.g., smart glasses), appliances, internet ofthings (IoT) devices, voice assistants, at-home touch screen displaysystems, and/or any other suitable user computing devices capable ofaccessing and communicating using local and/or global networks (e.g.,the network 154). The user devices 104 may be associated with employeesor with customers of the provider (e.g., customers at the FI). As such,the customer account database 118 may be further configured to storedevice information concerning each user device 104 associated with acustomer of the provider. Similarly, the employee database 144 may befurther configured to store device information pertaining to each userdevice 104 of an employee at a branch location. For example, the deviceinformation may include a device form (e.g., the type of user device104), a set of device capabilities (e.g., types of input/output devices,device mobility, device communication capabilities), device locationinformation, and/or device identification and authentication information(e.g., an encrypted device token for each user device 104, userauthentication information, such as a PIN or biometric data, associatedwith each user device 104, etc.).

The user devices 104 may each similarly include a network interface 124,a processing circuit 126, and an input/output device 134. The networkinterface 124, the processing circuit 126, and the input/output device134 may be structured and function substantially similar to and includethe same or similar components as the network interface 110, theprocessing circuit 112, and the input/output device 122 described above,with reference to the provider computing system 102. Therefore, itshould be understood that the description of the network interface 110,the processing circuit 112, and the input/output device 122 of theprovider computing system 102 provided above may be similarly applied tothe network interface 124, the processing circuit 126, and theinput/output device 134 of each of the user devices 104.

In some embodiments, the network interface 124 is similarly structuredand used to establish connections with other computing systems (e.g.,the provider computing system 102, the branch computing system 108,other user devices 104, and the smart tables 106) via the network 154.The network interface 124 may further include any or all of thecomponents discussed above, with reference to the network interface 110.

The processing circuit 126 similarly includes a memory 130 and aprocessor 128. The memory 130 and the processor 128 are substantiallysimilar to the memory 116 and the processor 114 described above.Accordingly, the user devices 104 are similarly configured to run avariety of application programs and store associated data in a databaseof the memory 130. For example, the user devices may be configured torun an application such as the user client application 132.

The user client application 132 may be substantially similar to theprovider client application 120, the branch client application 150, andthe smart table client application 218 (FIG. 2), but may instead bespecifically tailored to the user associated with the user devices 104.For example, the user client application 132 is similarly structured toselectively provide displays and/or audio/visual communications to eachuser device 104 to allow for improved interactions between a customerand branch employees, branch managers, and provider employees.

Particularly, the user client application 132 is configured tocommunicate with the provider computing system 102, the branch computingsystem 108, and the smart tables 106 to facilitate user interactionswith a smart table 106 during a banking session at a branch location. Assuch, the user devices 104 are communicably coupled to the providercomputing system 102 (e.g., through interactions with the providerclient application 120), the branch computing system 108 (e.g., throughinteractions with the branch client application 150), and the smarttables 106 (e.g., through interactions with the smart table clientapplication 218 (FIG. 2)).

The user client application 132 may therefore communicate with theprovider computing system 102, the smart tables 106, and the branchcomputing system 108 to perform a variety of functions. For example, theuser client application 132 is similarly configured to receive userinputs (e.g., via a user interface of the user device 104) to completefinancial transactions during a user session with a smart table 106,depending on whether the individual associated with the user device 104is an employee or a customer. Additionally, the user client application132 is configured to output information to a display of the user device104 regarding information on the financial transaction. For example, theuser client application 132 is configured to generate a user interfaceto show graphics regarding a financial history of a customer.

The user client application 132 is further configured to allow forcommunication with the provider client application 120 to allow a userassociated with the various user devices 104 to update accountinformation and/or provide feedback during a banking session with asmart table 106. Accordingly, the user client application 132facilitates effective communication with a branch manager, other branchemployees, the provider employees, and/or other customers (e.g., duringa banking session with two customers, such as a mother and daughter)during a connected session with a smart table 106.

The user client application 132 may also be structured to allow the userdevices 104 to retrieve and submit documents, forms, and/or any type ofnecessary information to and/or from a smart table 106 during anestablished session, as required to complete certain financial tasks. Insome instances, the user client application 132 may be configured toautomatically retrieve and/or submit documents, forms, or othernecessary information to and/or from a smart table 106 in response tothe establishment of a secure connection to the smart table 106. In someembodiments, the user client application 132 may be configured totemporarily store the various documents, forms, and/or necessaryinformation, which may then be selectively transmitted to the smarttable 106 in response to a user input from a customer or employee (e.g.,received via the input/output device 134).

In some embodiments, the user client application 132 may be configuredto temporarily store the various documents, forms, and/or necessaryinformation and then selectively transmit the various documents, forms,and/or necessary information to the smart table 106 in response to acustomer's arrival at a branch location. For example, the user device104 may automatically connect to the branch computing system 108 and/orthe one or more smart tables 106 when the user device 104 is withinrange of a network or communication device associated with the branchcomputing system 104 and/or the one or more smart tables 106.

In some embodiments, a customer or employee may identify various levelsof authority associated with each of the user devices 104. For example,in some implementations, a user may set a first user device 104 as aprimary user device and a second user device 104 as a secondary userdevice. In some instances, there may be various approved users of theuser devices 104, excluding the user, such as family members,caretakers, business partners for customers, or other branch employees,a branch manager, a supervising employee for employees at the branchlocation. As such, in some embodiments, a primary user device may havethe authority to veto or cancel the actions taken by a secondary userdevice.

Furthermore, the user client application 132 may be configured toprovide a device status for each user device 104 to the banking sessionmanagement circuit 210 (FIG. 2) of a smart table 106. The device statusmay include both a device location and an indication of whether therespective user device 104 is active. For example, the user clientapplication 132 may be configured to automatically, periodically, and/orselectively provide geographical location information to the bankingsession management circuit 210. Additionally, the user clientapplication 132 may be configured to send the banking session managementcircuit 210 a notification and/or an update when a given user device 104is active.

In some embodiments, a user device 104 may be considered active if, forexample, the user device 104 is currently being used (e.g., by acustomer or by an employee during a banking session with a smart table106), a user has indicated that the provider computing system 102, thebranch computing system 108, and/or the smart tables 106 are permittedto send/retrieve data to/from the user device 104, and/or the userdevice 104 is within a predetermined distance from the branch computingsystem 108 or one of the smart tables 106. In some embodiments, theremay be additional manners in which the user device 104 may be consideredactive.

The input/output device 134 of each user device 104 may functionsubstantially similar to and include the same or similar components asthe input/output device 122 previously described, with reference to theprovider computing system 102. As such, it should be understood that thedescription of the input/output device 122 provided above may also beapplied to the input/output device 134 of each of the user devices 104.In some embodiments, the input/output device 134 of each user device 104is similarly structured to receive communications from and providecommunications to a user (e.g., customer or employee) associated withthe plurality of user devices 104.

For example, the input/output device 134 may include one or more userinterfaces, which may include one or more biometric sensors (such as aniris scanner, a fingerprint scanner, a heart monitor that identifiescardiovascular signals, etc.). The input/output device 134 may alsoinclude components that provide perceptible outputs (such as displaysand light sources for visually-perceptible elements, a speaker foraudible elements, and haptics for perceptible signaling via touch, etc.)and/or that permit the user to enter inputs (such as a stylus or forcesensor for detecting pressure on a display screen). One or more userdevices 104 may include one or more locations sensors to allow the userdevices 104 to detect its location relative to other physical objects(e.g., a smart table 106 or other user devices) or geographic locations.Example locations sensors may include global positioning system (GPS)devices and other navigation and geolocation devices, digital compasses,gyroscopes and other orientation sensors, as well as proximity sensorsor other sensors that permit the user device 104 to determine thepresence and relative distance of nearby devices, objects, and/orlocations.

Still referring to FIG. 1, the smart table system 100 includes one ormore smart tables 106. The smart tables 106 may be tables of varyingsizes integrated with cash handling endpoints. Furthermore, the smarttables 106 may provide a shared graphical user interface for scenariosin which a display screen of a user device is not the right size for animproved and efficient customer experience. In some embodiments, each ofthe smart tables 106 are associated with a smart table identifier, suchas a numeric or alphanumeric code, to identify the respective smarttable to the branch computing system 108, the provider computing system102, and the user devices 104. For example, in response to walking intoa lobby of a branch location for a scheduled banking session, a userdevice 104 associated with the customer may indicate to the customerwhich smart table 106 to go to in order to initiate the session. Whiledescribed with regards to a FI, the smart tables 106 may be used inother scenarios. For example, the smart tables 106 may be used at a cardealership or car rental company, a hotel, a booking agent, and/or amedical office. The features of the smart tables 106 are described ingreater detail below, with reference to FIG. 2.

The smart table system 100 may include one or more tactile input devices156. The tactile input devices 156 may be devices with an adjustabletactile overlay on an independent touch screen. In some embodiments, thetactile input devices 156 may be an adjustable tactile overlay used inconjunction with the touchscreen of the smart table 106 to increase theefficiency of data entry and increase the functionality of the smarttable 106. In some embodiments, each of the tactile input devices 156are associated with a tactile input device identifier configured toidentify the respective tactile input device to the branch computingsystem 108, the provider computing system 102, the user device 104,and/or the smart table 106. In some instances, the tactile input deviceidentifier may be a numeric or alphanumeric code. While described withregards to a financial institution (FI) and in conjunction with a smarttable 106, the tactile input devices 156 may be used in other scenarios.The features of the tactile input device are described in greater detailbelow, with reference to FIG. 11.

Referring now to FIG. 2, a block diagram of the smart tables 106 isshown, according to some embodiments. The smart tables 106 eachsimilarly include a network interface 202, a processing circuit 204, andan input/output device 220. The network interface 202, the processingcircuit 204, and the input/output device 220 may function substantiallysimilar to and include the same or similar components as the networkinterface 110, the processing circuit 112, and the input/output device122 described above, with reference to the provider computing system102. Thus, it should be understood that the description of the networkinterface 110, the processing circuit 112, and the input/output device122 of the provider computing system 102 provided above may be similarlyapplied to the network interface 202, the processing circuit 204, andthe input/output device 220 of each of the smart tables 106.

For example, the network interface 202 is similarly structured and usedto establish connections with other computing systems (e.g., theprovider computing system 102, the branch computing system 108, the userdevices 104) via the network 154. The network interface 202 may furtherinclude any or all of the components discussed above, with reference tothe network interface 110.

The processing circuit 204 similarly includes a processor 206 and amemory 208. The processor 206 and the memory 208 are substantiallysimilar to the processor 114 and the memory 116 described above. Assuch, the smart tables 106 are similarly configured to run a variety ofapplication programs and store associated data in a database of thememory 208. For example, the smart tables 106 may be configured to runthe application the smart table client application 218.

The smart table client application 218 may be substantially similar tothe provider client application 120 and the branch client application150, but may instead be specifically for personalized banking sessionsbetween customers and employees at the bank. For example, the smarttable client application 218 is similarly structured to provide displaysto each customer user device 104 to facilitate improved interactionsbetween customers and specific branch employees associated with eachsmart table 106. Particularly, smart table client application 218 isconfigured to communicate with the provider computing system 102, thebranch computing system 108, and the user devices 104 to receiveinstructions and reminders from the provider computing system 102 and/orthe branch computing system 104 for the branch employees associated witheach smart table 106 to perform various tasks associated with a bankingsession. Accordingly, the smart tables 106 are communicably coupled tothe provider computing system 102 (e.g., through interactions with theprovider client application 120), the branch computing system 108 (e.g.,through interactions with the branch client application 150), and theuser devices 104 (e.g., through interactions with the user clientapplication 132).

The smart table client application 218 may therefore communicate withthe provider computing system 102, the branch computing system 108, andthe user devices 104 to perform several functions. For example, thesmart table client application 218 is configured to receive data fromthe provider computing system 102 and/or the branch computing system 104pertaining to necessary inputs for authenticating a particulartransaction during a banking session. The smart table client application218 is further configured to allow for communication with the providerclient application 120 to allow the various branch employees thatoperate the smart tables 106 to provide questions or comments regardingany concerns with the smart tables. As such, the smart table clientapplication 218 allows for the branch employees associated with thesmart tables 106 to communicate with the customer, branch manager,and/or provider employees throughout the process of a banking session.

In further embodiments, the smart table client application 218 maycommunicate with the tactile input device 156 via a tactile input deviceclient application 1110. Further, the smart table client application 218may be configured to sense the location of the tactile input device 156on the smart table 106 via various sensors. For example, the varioussensors may include Bluetooth™ sensors, Near Field Communication (NFC)sensors, conductive sensors, etc. Based on the sensed location, thesmart table client application 218 may rearrange various information andgraphics on a user interface displayed to the user to ensure that theinformation and graphics are not blocked by the tactile input device156. In some embodiments, wherein the tactile input device 156 does notcomprise a touchscreen, the smart table client application 218 mayrearrange the display of the smart table 106 to align a visual displayof a QWERTY keyboard, a 10-key keyboard, or any other suitable keyboardgraphic or designated input area that is necessary or desired for agiven task with the tactile input device 156. In some instances, thetactile input device 156 may be made of a transparent material, suchthat the visual of the keyboard graphic or designated input area isshown through the tactile input device.

The input/output device 220 of each smart table 106 may functionsubstantially similar to and include the same or similar components asthe input/output device 134 described above, with reference to the userdevices 104. Accordingly, it should be understood that the descriptionof the input/output device 134 provided above may also be applied to theinput/output device 220 of each of the smart tables 106. For example,the input/output device 220 of each smart table 106 is similarlystructured to receive communications from and provide communications tocustomers paired with a smart table 106 and to the branch employee orbranch employees associated with each smart table 106.

The processing circuit 204 also includes a banking session managementcircuit 210, an authentication circuit 212, a notification generationcircuit 214, and a cash dispenser management circuit 216, for example.In other embodiments, the processing circuit 204 may contain more orless components than shown in FIG. 2. The components of FIG. 2 are meantfor illustrative purposes only, and should not be regarded as limitingin any manner. The banking session management circuit 210 may beconfigured to detect a trigger event for a banking session with thesmart table 106. A banking session may include one customer (e.g., thesmart table 106 is configured as a self-service ATM), a branch employeeand a customer, or a branch employee and more than one customer,according to some embodiments. For example, two customers that have ajoint account together may participate in a banking session with abranch employee. In some embodiments, a trigger event includes detectinga user device 104 within a communication range of the smart table 106.In other embodiments, a trigger event includes the activation of aselectable icon on a graphical user interface of the smart table 106. Inresponse to detecting a trigger event, the banking session managementcircuit 210 may be configured to send instructions to the notificationgeneration circuit 214 to request input for customer and/or employeeauthentication.

In some embodiments, the banking session management circuit 210 isfurther configured to receive sensor data from the input/output device220 of the smart table 106. For example, the banking session managementcircuit 210 may be configured to receive camera data of documents that acustomer wants to scan and save, movement data from a motion detector,temperature sensor data, and so on. Additionally, the banking sessionmanagement circuit 210 may determine when to send reminders to a userdevice 104 of the branch employee regarding a banking session (e.g., tofill out a certain form, to pre-load a compartment of the smart table106) and/or when to send a session end reminder for a scheduled bankingsession. For example, the banking session management circuit 210 may beconfigured to track how much time is remaining in a scheduled session towrap up a financial transaction with the customer.

The authentication circuit 212 may be configured to determine whether auser is authenticated to initiate a banking session and/or to completecertain financial tasks. For example, the authentication circuit 212 maybe configured to request an authorization approval from the providercomputing system 102 of a received PIN or biometric input. In someembodiments, the authentication circuit 212 is also configured todetermine the level of authentication necessary to complete differenttypes of financial tasks (e.g., withdrawal cash, take out a loan, make anew investment, etc.). The authentication circuit 212 may be configuredto generate a score of how authenticated a user is during a bankingsession. For example, a user that entered both a biometric input and analphanumeric passcode may receive a first score of 100% authenticated,and a user that only entered a PIN may receive a second score of 50%authenticated. The authentication circuit 212 is also configured to sendinstructions to the cash dispenser management circuit 216 in response toreceiving an approved authorization (e.g., from the provider computingsystem via the network 154) to dispense cash to a customer for awithdrawal request.

The notification generation circuit 214 may be configured to createalerts regarding an upcoming banking session, an in-progress bankingsession, and/or a completed banking session, according to someembodiments. The notification generation circuit 214 may also receiveinstructions on the format of a notification from the banking sessionmanagement circuit 210. In some embodiments, the notification generationcircuit 214 is configured to instruct the input/output device 220 of thesmart table 106 to provide audible and/or visual output to a customerregarding information displayed during a banking session. For example,the notification generation circuit 214 may be configured to cause a NFCicon on a graphical user interface of the smart table 106 to flash toindicate to a user to place a user device 104 on the NFC icon to pair tothe smart table 106. As another example, the notification generationcircuit 214 may be configured to generate a notification that outputs avoice-over indicating the banking session will terminate within acertain time interval, such as a five minute warning to complete anyunfinished tasks.

Still referring to FIG. 2, the cash dispenser management circuit 216 maybe configured to control the use of the cash dispenser of the smarttable 106. In some embodiments, the cash dispenser management circuit216 is further configured to determine when the amount of available cashat the smart table 106 is below a threshold value (e.g., $100). The cashdispenser management circuit 216 may then instruct the notificationgeneration circuit 214 to create a notification of the low amount ofcash at the smart table 106 to the branch computing system 108 and/or auser device 104 (e.g., a branch manager user device 104). In someembodiments, the cash dispenser management circuit 216 is alsoconfigured to transmit an instruction to update a balance of thecustomer account to the provider computing system 102, for example,after the transaction request is completed. The cash dispensermanagement circuit 216 may further be configured to instruct theinput/output device 220 of the smart table 106 to print a receipt withtransaction details, such as the amount of cash withdrawn, the time ofthe completed transaction, and/or an updated balance for the customeraccount used to complete the transaction.

The use of the smart table 106 within the smart table system 100 maybeneficially reduce significant amounts of time to complete financialtransactions during a banking session and/or fill out paperwork forms.Furthermore, the smart tables 106 may help improve transparency ofcustomer account information and employee services and increaseface-to-face time with the branch employees. By providing a largergraphical user interface to share customer account information, ratherthan on a tiny screen on a single user device, the smart tables 106 alsoincrease the amount of inclusion for each party participating in thebanking session. The smart tables 106 may additionally help informcustomers of several choices and advise the customers by displayinginformation from the branch employee regarding the customer accountinformation utilizing visual tools. In some embodiments, the visualtools may include pie charts, bar graphs, scatterplots, user graphics,and so on. The smart tables 106 may be configured such that a customersits while using, or may be configured such that a customer stands whileusing.

Referring now to FIG. 3, a flow diagram of a method 300 for initiating asession between one or more user devices 104 and a smart table 106 isshown, according to some embodiments. The method 300 may be provided byand/or accessible by the provider client application 120, the branchclient application 150, the user client application 132, and the smarttable client application 218, for example. The method 300 may beperformed by the smart table system 100 described above pertaining toFIGS. 1 and 2. In some embodiments, the method 300 begins in response toreceiving, by a smart table 106, a session trigger event. A sessiontrigger event may be any event that triggers the beginning of a sessionbetween the smart table 106 and a user device 104. For example, when acustomer is within a certain proximity of the smart table 106, the userdevice 104 associated with the customer that the customer is holding maybe within a wireless communication range of various devices (e.g., thebranch computing system 108 and/or the smart table 106) associated withthe branch location. In response to entering the wireless communicationrange, the respective user device 104 may be configured to automaticallyrequest the customer, via the user device 104, to enter confirmation toestablish a secure connection with the smart table 106. As such, thesecurity of the banking session may increase, as a customer may berequired to be within a certain proximity of the smart table 106 tobegin the banking session. In some embodiments, similarly, a user device104 of an employee scheduled to be running a banking session for thesmart table 106 may also be required to be within proximity of the smarttable 106 in order to initiate the banking session. A session triggerevent may also include receiving an input via input/output device 220,such as receiving a user interaction via a touch screen display of thesmart table 106. In other embodiments, a session trigger event mayinclude a customer or employee logging into a user client application132 on a user device 104. In additional embodiments, a session triggerevent may occur at a specific time, such as in response to the bankingsession management circuit determining there is a scheduled bankingsession at a smart table 106 at a specific time. In some embodiments,the smart table 106 may be configured to operate in a low power mode or“sleep mode” until a session trigger event is received.

At 302, the method 300 includes generating and transmitting anotification to a customer device (e.g., a user device 104) to providean input for authentication. In some embodiments, the notificationgeneration circuit 214 is configured to execute step 302 in response toreceiving an instruction from the banking session management circuit210. The notification generation circuit 214 may be configured togenerate a notification requesting user authentication based oninformation received, via the network 154, from the smart tablemanagement circuit 148 and customer account database 118. For example,specific smart tables 106 may require higher levels of authenticationbefore a user may initiate a banking session based on the capabilitiesof the smart table. Additionally, the customer account database 118 mayhave stored customer preferences indicating one or more types of inputthe customer wants to use for authenticating a banking session. Inputfor authentication may include a personal identification number (PIN), abiometric input (e.g., a fingerprint, a palm print, an eye scan, a voicesample, etc.), an alphanumeric passcode, a barcode, a QR code, aphysical key, an electronic key (e.g., a token stored on the user device104 of the customer), a physical or mobile wallet card (e.g., a creditcard with chip technology, a virtual bank card), and so on. In someembodiments, the generated notification may include audible or tactileoutput when received by the user device 104. For example, in response toreceiving the generated notification, the user device 104 may create anaudible sound, via the input/output device 134, to catch the attentionof the customer and/or an employee working with the customer and/or maycause the user device 104 to vibrate.

In other embodiments, instead of transmitting the notification to a userdevice 104, the notification requesting an input to authenticate thecustomer is shown on a display screen of the smart table 106. Forexample, the notification generation circuit 214 may generate anotification requesting a customer to place a palm on a highlighted areaof the display screen of the smart table 106. As another example, thenotification generation circuit 214 may provide a notification shown onthe display screen of the smart table 106 asking a customer to enter acustomer PIN on the customer's user device 104. In some embodiments, thegenerated notification also includes a message to place the user device104 associated with the customer on a particular area of the smart table106. For example, a highlighted area may indicate where to place theuser device 104 in order to facilitate using near-field communicationdata exchange.

The input to authenticate initiation of a banking session is received atstep 304. In some embodiments, the authentication circuit 212 isconfigured to receive the input to authorize initiating the bankingsession. One or more inputs may be received at step 304, according tosome embodiments. For example, in some banking sessions, more than onecustomer may be detected and/or scheduled to participate in the bankingsession. As such, the authentication circuit 212 may receive inputs fromeach customer for the banking session. Additionally, an input toauthenticate an employee scheduled to participate in the banking sessionmay also be received at 304. For example, for banking sessions scheduledto conduct transactions with higher security, a branch manager may berequired in order to initiate the banking session. As such,authentication inputs may be received from the customer and the branchmanager at step 304.

In some embodiments, the inputs are received via the user devices 104and transmitted to the smart table 106 via the network 154. In otherembodiments, the one or more inputs may be received directly by thesmart table 106 via the input/output device 220. For example, a PIN forauthentication may be entered via a user interface of the customer'suser device 104, or a fingerprint may be entered via the input/outputdevice 220 (e.g., a fingerprint scanner) of the smart table 106.Beneficially, a customer may then enter personal authenticationinformation in a more private setting, rather than entering personalauthentication information on the smart table 106. As such, the securityof the customer's personal information may be improved.

At step 306, the method 300 includes determining whether one or moreusers are authenticated to initiate the banking session. In someembodiments, the authentication circuit 212 is configured to determinewhether authentication for the banking session is successful. Thenetwork interface 202 may transmit, via the network 154, the receivedinput to the branch computing system 108 and/or the provider computingsystem 102. In some embodiments, the provider computing system 102and/or the branch computing system 108 then determine whether thereceived input matches user information stored in a database (e.g., incustomer account database 118, in employee database 144). For example,the provider computing system 102 determines whether a device tokenreceived from the user device 104 matches a token stored in a tokenvault of the customer account database 118. The network interface 202may then receive confirmation or a denial of authentication for the oneor more users (e.g., a customer, a customer and an employee, more thanone customer, etc.). In some embodiments, the authentication circuit 212is configured to execute step 306 at certain intervals throughout abanking session. For example, after a predetermined time interval, or atthe end of a scheduled banking session, the authentication circuit 212may be configured to re-authenticate the one or more customers and/oremployee.

In response to determining one or more of the users were notauthenticated, the method 300 proceeds to step 308. The method 300includes generating and transmitting a notification for an unauthorizedaccess attempt at step 308. In some embodiments, the notificationgeneration circuit 214 is configured to execute the operations at 308.The notification generation circuit 214 may be configured to generate atext notification, an email notification, an automated voiceovernotification, and/or any kind of alert to notify a user. Thenotification generation circuit 214 may be configured to include detailsconcerning the access attempt in the generated notification. Forexample, the notification may include branch location information (e.g.,name, address) and/or a timestamp of when the attempt to initiate abanking session was denied. In some embodiments, the notification alsomay include contact information for a branch manager and instructionsconcerning the security of a customer's personal data. For example, thegenerated notification may include options to view user account details,transaction history, previous banking session history, and so on. Thegenerated notification may also include selectable options to change oneor more inputs for authentication (e.g., change a user passcode, changea user PIN, etc.) and/or user preferences (e.g., preferences forincreased security before access is granted to customer information). Insome embodiments, the notification is transmitted to a user device 104associated with a customer. The notification may also be transmitted,via the network 154, to a user device 104 associated with a branchmanager and/or an employee assigned to a scheduled banking session.

On the other hand, if the authentication circuit 212 determines at step306 that the one or more users are successfully authenticated, themethod 300 proceeds to step 310. At step 310, the method 300 includesgenerating and providing a notification of a successful pairing betweencustomer device (e.g., user device 104) and the smart table 106 for thebanking session. In some embodiments, the notification generationcircuit 214 is configured to generate a text alert or email alertindicating the establishment of a secure communication session with thesmart table 106. The type of generated notification (e.g., email, text,phone call, etc.) may be based on user preferences. For example, thebanking session management circuit 210 may receive session preferencesfor a customer stored in customer account database 118. The bankingsession preferences may include the kind of notifications the customerwants to receive. The preferences may also include information on whereto direct the generated notification. For example, customer preferencesmay include contact information (e.g., an email of a parent of thecustomer, a phone number, etc.) to send the generated notification. Assuch, in some embodiments, the notification may be provided to one ormore user devices 104. The generated notification for a successfulpairing between the customer user device 104 and the smart table 106 mayalso be provided via the input/output device 220 of the smart table 106.For example, the smart table 106 may show the notification on a displayscreen.

At step 312, the method 300 includes retrieving customer accountinformation for the customer account associated with the pair customeruser device 104. In some embodiments, the banking session managementcircuit 210 is configured to execute step 312. The banking sessionmanagement circuit 210 may be configured to request, via the networkinterface 202, customer account information from the provider computingsystem 102. In some embodiments, the amount of customer accountinformation retrieved is relative to the security of the bankingsession. For example, the customer account information retrieved isrelative to the type of input received for user authentication. As anexample, if only a passcode was entered, the customer accountinformation that is retrieved may be more limited than if a passcode anda biometric input were entered to authenticate the customer. In someembodiments, customer account information may include previous bankingsession history, transaction history for the customer account, balancesfor various accounts (e.g., savings accounts, checking accounts, creditcard accounts), loan information, mortgage information, personalinformation (e.g., name, address, age, education, occupation, salary,etc.), credit card debt, current investments, retirement plans, savingsgoals, and so on. The banking session management circuit 210 may also beconfigured to pull specific documents concerning planned transactionsfor a scheduled banking session at 312. For example, a prepared documentregarding a loan may be retrieved at step 312 for a branch employee toreview with the customer during the scheduled banking session.

Once the customer account information has been retrieved, at step 314,the customer account information may be displayed on the smart table 106for the authenticated banking session. In some embodiments, the customeraccount information may be displayed in a customer area of a displayscreen of the smart table 106. In other embodiments, the customeraccount information may be displayed on the customer's user device 104rather than on a display screen of the smart table 106. For example, forcertain customer account information that is more confidential, such asa social security number, and/or customer account information that acustomer indicated in preferences should not be shown during a bankingsession on a smart table, such as a salary or the customer's overallfinancial worth, the banking session management circuit 210 may beconfigured to only provide that information on the customer's userdevice 104. In some embodiments, the customer account information may bedisplayed using tables, graphics, and/or other visual tools to helpconvey the data to the customer in a meaningful manner. For example,concerning retirement, a graphic may show a portion of the customer'scurrent earnings that should be set aside for retirement and theprogress the customer has made in saving for retirement over a specificperiod of time.

Referring now to FIG. 4, an illustration of various configurations ofthe smart table 106 are shown, according to some embodiments. Aperspective view 402 of a smart table 106 depicts a storage compartmentbeneath a top surface of the smart table 106. In some embodiments, thecash dispenser of the smart table 106 may be accessed by lifting a topsurface of the smart table 106. As such, the cash dispenser may easilybe serviced by lifting the top surface of the smart table 106, coveringthe storage compartment. In other embodiments, a storage compartment ofthe smart table 106 may be accessed by sliding the top surface to a sideof the smart table 106, rather than lifting the top surface. Aperspective view 404 of a smart table 106 shows an integration ofstorage compartments for the smart table 106 and a digitally enabled,touch screen display, according to some embodiments. A perspective view406 of a smart table 106 depicts a touch screen display encompassing thetop surface of the smart table 106. In some embodiments, the smart table106 may not include a cash dispenser, as shown in perspective view 406.The views shown in FIG. 4 are meant to be illustrative in purpose only,and should not be regarded as limiting in any manner.

Referring now to FIG. 5, an illustration of additional configurations ofthe smart table is shown, according to some embodiments. Perspectiveview 502 depicts a smart table 106 with a touch screen display and legs506 at a set height. Perspective view 504 shows a smart table 106including a touch screen display and legs 508. In some embodiments, thelegs 508 may be adjusted to varying heights based on user preference.For example, a user may increase or decrease the height of the smarttable 106 by operating motorized lifting columns to increase or decreasethe height of the legs 508. In some embodiments, the motorized liftingcolumns of the legs 508 are activated using a switch on the smart table106. In other embodiments, the height of the smart table 106 isincreased or decreased by entering an input via a touch screen of thesmart table 106.

Referring now to FIG. 6, an illustration of a user interface 600 of thesmart table 106 and paired user devices 104 is shown, according to someembodiments. The user interface 600 may be provided by the smart tableclient application 218. In some embodiments, the user interface 600 isgenerated and displayed, via an input/output device 220, by the bankingsession management circuit 210. The user interface 600 includes accountsummary window 604, for example. The account summary window 604 mayinclude a name, address, photo identification, and contact informationfor a customer. In some embodiments, the account summary window 604 isdisplayed in response to receiving a selection of a profile icon on theuser interface 600. The user interface 600 also includes a device area602. In some embodiments, the device area 602 includes a charging iconand a wireless connection icon. The connection icon may indicate to oneor more users (e.g., a customer, two customers, a customer and anemployee, etc.) where to place a user device 104 in order to pair to thesmart table 106. As such, the connection icons shown on the userinterface 600 may be used as indicators of the locations of NFC tagswithin the smart table 106. In some embodiments, the user interface 600may utilize different colors to indicate a successful pairing and anunsuccessful pairing in device area 602. For example, the connectionicon may turn green in response to a successful pairing to therespective user device 104 placed over the connection icon. AlthoughFIG. 6 depicts two user devices 104, the smart table 106 may beconfigured to pair to more than two different user devices 104,according to some embodiments.

Referring now to FIG. 7, an illustration 700 of a user interface of thesmart table 106 configured to receive an input from a customer orprovider representative is shown, according to some embodiments. Theillustration 700 depicts a keyboard 702, a customer device 704, and anemployee device 706. The customer device 704 and the employee device 706may both be the same or similar as the user devices 104 described above.In some embodiments, the keyboard 702 is displayed on a user interfaceof the smart table 106 to provide an input for the customer. Thekeyboard 702 may be displayed to enter new information, such as a changeof address for the customer. In some embodiments, the keyboard 702 isoriented on a display screen of the smart table 106 based on whether acustomer or an employee needs to enter information. For example, thesmart table 106 may serve as a desk for a branch employee (e.g., abanker). As such, while sitting down at the smart table 106, thecustomer and the branch employee may be seated on opposite sides of thesmart table 106. In some embodiments, the input/output device 220 of thesmart table 106 is configured to determine an orientation and positionfor the keyboard 702 based on data received from sensors and/or camerasof the smart table 106.

Referring now to FIG. 8, an illustration 800 of the smart table 106including a dispensing mechanism 802 is shown, according to someembodiments. The dispensing mechanism 802 can be a cash dispenser,though it will be appreciated that the dispensing mechanism 802 can beconfigured to dispense any type of item, such as cash, a receipt,checks, stamps, and so on. Accordingly, the smart table 106 maybeneficially be utilized as an automated teller machine (ATM). In someembodiments, the smart table 106 may be used as an assisted-service ATM,as shown in FIG. 7. The smart table 106 may also function as a stationfor tellers at a branch location. In other embodiments, the smart table106 may be used as a self-service ATM, without using employees tosupervise the transaction at the smart table 106. The smart table 106may be configured to pair with the user device 104 of the customerbefore dispensing cash via the dispensing mechanism 802. For example,the dispenser management circuit 216 is configured to receive approvalfrom the authentication circuit 212 before providing cash to a customerusing the smart table 106.

Referring now to FIG. 9, an illustration 902 of various user interfaceorientations displayable by the smart table 106 is shown, according tosome embodiments. A first user interface orientation 902 includes a userinterface of a smart table 106 with half of a customer interface areaand half of a branch employee interface area. In some embodiments, thebranch employee interface area is rotated 180 degrees from the customerinterface area in a traditional setting for when the branch employee ison an opposite side of the smart table 106 from the customer. A seconduser interface orientation 904 includes a user interface of the smarttable 106 with the customer interface area and the branch employeeinterface area rotated 90 degrees from the customer interface area for amore casual setting. A third user interface orientation 906 includes auser interface of the smart table 106 with one interface area for boththe customer and the branch employee. In some embodiments, the thirduser interface orientation 906 shows the customer interface area forwhen the customer and the branch employee are on the same side of thesmart table 106, for example.

Referring now to FIG. 10, an illustration of example user interfaces ofthe user device 104 when the user device 104 is paired to the smarttable 106 is shown, according to some embodiments. FIG. 10 includes userinterface 1002 and user interface 1004. In various embodiments, the userinterface 1002 and the user interface 1004 are generated by the smarttable system 100 described above with reference to FIG. 1. In someembodiments, the user interface 1002 and the user interface 1004 aregenerated during the method 300 described above with reference to FIG.3. The user interface 1002 may be displayed on a user device 104associated with a customer attempting to pair to a smart table 106, forexample. The user interface 1002 may include activatable icons forselecting various options regarding authenticating the customer. In someembodiments, the user interface 1002 includes a password activatableicon 1006 and a new customer activatable icon 1008. In response toreceiving a user selection of the password activatable icon 1006, aprompt, generated by the notification generation circuit 214, to enter apassword for customer authentication may be displayed. Upon selection ofthe new customer activatable icon 1008, the notification generationcircuit 214 may generate and display a new user interface requesting theuser to fill out information to create an account (e.g., a bank accountassociated with the provider).

The user interface 1004 may be displayed on the user device 104 inresponse to successful authentication and pairing with the smart table106. In some embodiments, the user interface 1004 includes activatableicons list 1010 for selecting various options regarding accounts of thecustomer. For example, the activatable icons list 1010 may includeoptions to view information pertaining to a checking account, a savingsaccount, a debit card, a credit card, and/or foreign exchange. The userinterface 1004 may also include a cancel activatable option 1012. Insome embodiments, in response to selection of the cancel activatableoption 1012, the banking session ends and the established connectionbetween the smart table 106 and the one or more paired user devices 104ends. In some embodiments, the user device 104 may return to a home pageof the user client application 132 in response to receiving a selectionof the cancel activatable option 1012.

The terms selectable and activatable are used interchangeably herein.Selectable/activatable icons presented as part of example GUIs may causea signal to be generated upon selection/activation. The signal may betransmitted to a system, device, or application to indicate to thedevice, system, or application which icon has been selected, and thedevice, system, or application may respond accordingly.

Referring now to FIG. 11, a block diagram of the tactile input devices156 is shown, according to some embodiments. As illustrated, each of thetactile input devices 156 may include a network interface 1102, aprocessing circuit 1104, and an input/output circuit 1120 as well as akey inflation device 1114. The network interface 1102 and the processingcircuit 1104 may function substantially similar to and include the sameor similar components as the network interface 110 and the processingcircuit 112 described above, with reference to the provider computingsystem 102. Thus, it should be understood that the description of thenetwork interface 110 and the processing circuit 112 of the providercomputing system 102, provided above, may be similarly applied to thenetwork interface 1102 and the processing circuit 1104 of each of thetactile input devices 156.

For example, the network interface 1102 is similarly structured and usedto establish connections with other computing systems (e.g., theprovider computing system 102, the branch computing system 108) via thenetwork 154. The network interface 1102 may further include any or allof the components discussed above, with reference to network interface110. Further, the network interface 1102 may also be structured and usedto establish a connection between the tactile input devices 156 and thesmart table 106. For example, in some instances, the network interface110 may be configured to provide communication between the tactile inputdevices 156 and the smart table via a Bluetooth™, Wi-Fi™, and/or anear-field communication (NFC) connection.

The processing circuit 1104 similarly includes a processor 1106 and amemory 1108. The processor 1106 and the memory 1108 are substantiallysimilar to the processor 114 and the memory 116 described above. Assuch, the tactile input devices 156 are similarly configured to run avariety of application programs and store associated in a database ofthe memory 1108. For example, the tactile input devices 156 may beconfigured to run the tactile input device client application 1110.

The processing circuit 1104 may also include an authentication circuit1112 for example. In other embodiments, the processing circuit 1104 maycontain more or less components than shown in FIG. 11. The components ofFIG. 11 are meant for illustrative purposes only, and should not beregarded as limiting in any manner.

The input/output circuit 1120 of each tactile input device 156 mayfunction substantially similar to and include the same or similarcomponents as the input/output device 220 described above, withreference to the smart table 106. Accordingly, it should be understoodthat the description of the input/output device 220 provided above mayalso be applied to the input/output circuit 1120 of each of the tactileinput devices 156.

For example, the input/output circuit 1120 of each tactile input device156 is similarly structured to receive communications from and providecommunications to customers and one or more branch employees associatedwith each tactile input device 156. In some embodiments, theinput/output circuit 1120 may include a biometric scanner that isconfigured to recognize various biometric identifiers (e.g.,finger/thumb prints, facial recognition, voice recognition). In furtherembodiments, the input/output circuit 1120 may comprise a scale-typedevice that is structured to measure the weight of an item on thesurface of the tactile input device 156. For example, in one embodiment,the tactile input device 156 may be used to determine the weight of asafety deposit box placed on the surface of the tactile input device156.

In some instances, the tactile input device client application 1110 mayhave many of the same capabilities of the smart table client application218. For example, the tactile input device client application 1110 maybe configured to communicate with the provider computing system 102, thebranch computing system 108, and smart table 106 to receive instructionsand reminders from the provider computing system 102, the branchcomputing system 104, and/or the smart table 106 for the branchemployees associated with each tactile input device 156 to performvarious tasks associated with a banking session. Accordingly, thetactile input devices 156 may be communicably coupled to the providercomputing system 102 (e.g., through interactions with the providerclient application 120), and the branch computing system 108 (e.g.,through interactions with the branch client application 150. Further,the tactile input device client application 1110 may also becommunicably coupled to the smart table 106 (e.g., through interactionswith the smart table client application 218).

The authentication circuit 1112 may be configured to determine whether auser is authenticated to initiate a banking session and/or to completecertain financial tasks. For example, the authentication circuit 1112may be configured to receive a PIN or a biometric input from a user(e.g., a bank employee or a customer). The authentication circuit 1112may then be configured to request an authorization approval from theprovider computing system 102 based on the received PIN or biometricinput. In some instances, the authentication circuit 1112 may beconfigured to generate an authentication score for a user is during abanking session. For example, a user that enters both a biometric inputand an alphanumeric passcode may receive a first authentication score of100%. Conversely, a user that only enters a PIN may receive a secondauthentication score of 50%.

The key inflation device 1114 may be configured to receive configurationinformation from the tactile input device client application 1110 basedon a necessary configuration for a given action. Depending on theconfiguration information received from the tactile input device clientapplication 1110, the key inflation device 1114 is configured toselectively inflate various areas of the tactile input device 156 toprovide various tactile input layouts. For example, in some instances,the tactile input layouts may include a QWERTY keyboard layout, a 10-keykeyboard layout, an authorization layout, a signature box layout, aweight measurement layout, and/or any other necessary layout for a givenaction.

In some embodiments, the key inflation device 1114 may include a dialconfigured to change the pressure within various input areas on thesurface of the tactile input device 156 and a device configured to routeinflation fluid to the correct input areas to form the necessary tactileinputs (e.g., the inflatable keys 1304, shown in FIG. 13). In otherembodiments, the input areas may be inflated by a pump configured toselectively pressurize a hydraulic circuit having selectively actuatablevalves configured to route the inflation fluid to the correct inputareas. In other embodiments, the input areas may be inflated usingvarious other suitable hydraulic, mechanical, and/or electromechanicalmethods, as deemed appropriate for a given application. In someembodiments, various layouts are attained by inflating separate layersof an overlay. In other embodiments, the key inflation device 1114 maydetermine individual input areas (e.g., keys or buttons) to inflate thatwould produce the desired layout for a given application.

In one embodiment, a banking session may take place at a smart table106, but may require authorization by a supervisor of the branchemployee. In this instance, the banking session may be continued on thetactile input device 156, which may be physically taken to thesupervisor for authorization. Upon authorization, the tactile inputdevice 156 may then be returned to the smart table 106 where the bankingsession may then resume.

In another embodiment, the tactile input device client application 1110may receive a required tactile layout from the smart table 106. In thisinstance, the tactile input device client application 1110 may thencommunicate the required tactile layout to the key inflation device1114. For example, the smart table client application 218 may indicatethat an alphanumeric input is required, prompting an alphanumeric inputdetermination. The smart table client application 218 may thencommunicate the necessary input to the tactile input client application1110, which then relays a particular key inflation layout to the keyinflation device 1114.

The use of the tactile input device 156 with the smart table system 100may beneficially reduce significant amounts of time to completefinancial transactions during a banking session and/or fill outpaperwork forms. For example, the user may be able to input informationmore quickly and more easily check for mistakes in the entry. This isdue to the ability of the user to enter information without needing tolook where they are typing as the location of the hands of the user isable to be referenced by the keys (e.g., similar to using a standardkeyboard). Furthermore, the tactile input device 156 may improve bankingsessions by making the input device more dynamic and able to start abanking session, or authorize a banking session remotely. For example, acustomer may be able to enter general banking session information (e.g.,name, desired transaction) prior to an appointment at the smart table106, where the information entered on the tactile input device 156 isable to be automatically transferred to the smart table 106.

Referring now to FIG. 12, an illustration of a tactile input device 156on the smart table 106 is shown, according to some embodiments. In someembodiments, the smart table 106 senses the placement of the tactileinput device 156 on the surface of the smart table 106. For example, thesmart table 106 may determine the location of the tactile input device156 and rearrange the layout of the user interface of the smart table106 to include a tactile input device area 1202 and an unobstructed area1204. The tactile input device area 1202 may be the area of the userinterface on the smart table 106 where the tactile input device 156 isplaced on the smart table 106. The unobstructed area 1204 may be thearea of the user interface on the smart table 106 that is unobstructedby the tactile input device 156 (e.g., where the tactile input device156 is not covering the surface of the smart table 106). In someembodiments, the tactile input device 156 may include a touch screen. Inthese instances, the tactile input device 156 may be configured toprompt the smart table 106 to not display anything within the tactileinput device area 1202 underneath the tactile input device 156. In otherembodiments, the tactile input device 156 may alternatively beconfigured to utilize the touch screen of the smart table 106. Forexample, the tactile input device 156 may be sufficiently flexibleand/or heat transmitting to allow for a user's touch to be conductedthere through onto the touchscreen of the smart table 106. In theseembodiments, the smart table 106 may display an appropriate layoutunderneath the tactile input device 156 within the tactile input devicearea 1202, such that various touch screen keys or buttons are alignedwith the input areas (e.g., keys or buttons) formed by the key inflationdevice 1114. In some instances, the tactile input device 156 may includea transparent touch screen configured to detect user inputs and transmitthe user inputs to the smart table 106. In these instances, although thetactile input device is not utilizing the touch screen of the smarttable 106, the smart table 106 may still display the appropriate layoutunderneath the tactile input device 156 to show the user the appropriatelayout for entering information through the transparent touch screen ofthe tactile input device 156.

Referring now to FIG. 13, an illustration of a side view of a tactileinput device 156 is shown, according to an example embodiment. In someembodiments, the tactile input device 156 has pads 1302. In someinstances, the pads 1302 may be arranged at the four corners on thebase. In other instances, the pads 1302 may be arranged in otherorientations. In some embodiments these pads are conductive and cancommunicate to the smart table 106 the position of the tactile inputdevice 156. In further embodiments, the pads 1302 may be used to measurethe weight of a safety deposit box. The pads 1302 may contain a straingauge load cell to determine said weight of the safety deposit box. Insome embodiments, such as when the tactile input device 156 isconfigured to conduct the user's touch there through onto thetouchscreen of the smart table 106, the tactile input device 156 may notinclude the pads 1302. In some embodiments, inflatable keys 1304 (e.g.,formed by the key inflation device 1114) may be rounded, as shown inFIG. 13. In other embodiments the inflatable keys 1304 may form variousother another shape (e.g., crescent, v-shaped).

In some embodiments, the tactile input device 156 may have a dial 1306to adjust the pressure in the inflatable keys 1304. In furtherembodiments, the pressure adjustment can be performed using variousother mechanical and/or electromechanical methods (e.g., slider,increase/decrease buttons). The tactile input device 156 may alsoinclude a power button 1308. In further embodiments the overlay of thetactile input device 156 may have an anti-microbial surface (e.g.,anti-microbial additives). In further embodiments, the display of thetactile input device 156 may have the ability to heat to a temperatureto kill bacteria on the surface. In another embodiment, the display maybe configured to display ultraviolet (UV) light that works to killviruses on the tactile input device 156.

Referring now to FIG. 14, an illustration of a tactile user interface ofthe tactile input device 156 is shown configured in an alphanumerickeyboard layout 1400, according to an example embodiment. In someembodiments, alphanumeric entries may be required for various givenactions performed by the smart table 106. Accordingly, the keyboardlayout 1400 may be used in these instances where letters and/or numbersare required (e.g., personal information, account information). Asillustrated, the keyboard layout 1400 may be provided as a QWERTYkeyboard layout. In some other instances, the keyboard layout 1400 maybe provided as various other types of keyboard layouts (e.g., Colemak,AZERTY, Dvorak, Neo, or any other suitable type of keyboard layout). Asillustrated, in some instances, the inflatable keys 1304 may be providedin a crescent shape. As discussed above, the inflatable keys 1304 may beprovided in various other shapes.

Referring now to FIG. 15, an illustration of a tactile user interface ofthe tactile input device 156 configured in a numeric keypad layout 1500is shown, according to an example embodiment. In some embodiments,numeric and mathematical entries may be required (e.g., enteringmonetary values, summing deposits) for various given actions performedby the smart table 106. Accordingly, the numeric keypad layout 1500 maybe used in these instances to allow for these necessary entries. Asillustrated, the inflatable keys 1304 may be provided in the lower rightcorner. In other embodiments, the inflatable keys 1304 could be providedon the left, centered, or located in another location, as deemedappropriate for a given application. In further embodiments, the tactileinput device 156 may be a different size. For example, the tactile inputdevice 156 may be sized depending on an intended layout for the tactileinput device. For example, in some instances, the tactile input device156 may be sized to more accurately fit the numeric keypad layout 1500.In other instances, the tactile input device 156 may be sized to fitvarious other layouts described herein.

Referring now to FIG. 16, an illustration of a tactile user interface ofthe tactile input device 156 configured in an authentication layout 1600is shown, according to an example embodiment. In some embodiments, theemployee and/or the customer may be required to authenticate theiridentities for various given actions performed by the smart table 106.In some instances, the smart table 106 may utilize the tactile inputdevice 156 to perform various authentication activities. Accordingly, inthese instances, the tactile input device 156 may provide theauthentication layout 1600. The authentication layout 1600 may allow forthe input of both biometric data (e.g., thumb scan) via a biometricsample area 1602 and a personal identification number (PIN) on a 10-keyPIN arrangement of inflatable keys 1304.

In some embodiments, the tactile input device 156 allows for anencrypted separation between the tactile input device 156 and the smarttable 106. For example, the PIN may be encrypted and sent to the smarttable 106 where it is decrypted. For example, the entering of the PINmay need to be payment card industry (PCI) compliant. In theseinstances, the tactile input device 106 may allow for compliance withthe PCI data security standards. In further embodiments, the tactileinput device 156 may be a different size. For example, the tactile inputdevice 156 may be sized to more exactly fit the authentication layout1600.

Referring now to FIG. 17, an illustration of the tactile input device156 configured in a signature layout 1700 is shown, according to anexample embodiment. In some embodiments, the smart table 106 may requirethe signature of a branch employee or customer. The tactile input device156 may show a user interface of a signature box 1702, with the signee'sname 1704 and the date of signature 1706. In some embodiments, the usermay sign the screen of the tactile input device utilizing a stylus or afinger. In these instances, the tactile input device 156 may beconfigured to scan the finger of the user for biometric data, as a formof authentication. In some embodiments, a camera or series of camerasabove the smart table 106 may be activated to record the customersigning. This may function as a multimedia way of capturing consent.

In some embodiments, the smart table may require multiple signaturesfrom multiple signees. In these instances, the tactile input device 156may generate multiple signature boxes 1702. In further embodiments, thetactile input device 156 may be a different size. For example, thetactile input device 156 may be sized to more exactly fit the signaturelayout 1700

Referring now to FIG. 18, an illustration of the tactile input device156 configured in a scale layout 1800 is shown, according to an exampleembodiment. In some instances, the tactile input device 156 may beconfigured to measure the weight of an item (e.g., a safety deposit box,a watch, currency). In these instances, the tactile input device 156 maybe arranged in the scale layout 1800. The tactile input device 156 mayuse a strain gauge load cell in the body of the tactile input device 156or the pads 1302 to measure the weight of an item. It should beappreciated that this is only one of a number of other ways the tactileinput device may measure the weight of an item. In some embodiments, thetactile input device 156 may warn the user to place the tactile inputdevice 156 on the floor or separate table prior to weighing the safetydeposit box. In further embodiments, the branch employee may be promptedby the tactile input device 156 to place a safety deposit box or otheritem on the top surface to measure the weight.

It should be appreciated that, in some cases, the tactile input device156 may be sized according to the intended interface layout (e.g.,keyboard layout 1400 the various interface layouts be provided that issmaller than the depicted tactile input device 156, such that thenumeric inflated keys of the numeric keypad layout 1500 substantiallyfill the surface of the tactile input device 156. Accordingly, byproviding a smaller tactile input device 156, the tactile input device156 may cover a smaller portion of the smart table 106, thereby allowingfor the unobstructed area 1204 to be larger. By providing a largerunobstructed area 1204, the smart table 106 may have additional roomwithin which to provide various information and/or graphics to the uservia the interface of the smart table 106.

Referring now to FIG. 19, a flow diagram of a method 1900 for utilizingthe tactile input device 156 as a user input for the smart table 106 isshown, according to an example embodiment. The method 1900 may beperformed by the smart table system 100 described above, with referenceto FIGS. 1, 2, and 11. It should be appreciated that the steps of themethod 1900 may be performed by either the smart table 106 or thetactile input device 156. For example, the tactile input device 156 maybe functional independent of the smart table 106. In some embodiments,method 1900 begins by the tactile input device 156 being placed on thesurface of the smart table 106. The smart table 106 may then beconfigured to sense the placement of the tactile input device 156 on thesmart table 106, at step 1902. In other embodiments, the method 1900 maybegin in various other manners. For example, in some instances, thetactile input device 156 may be a paired to the smart table 106 (e.g.,via a Wi-Fi™ connection or a Bluetooth™ connection), and the method 1900may alternatively start with an initiation of a banking session byeither of the smart table 106 or the tactile input device 156.

Once the tactile input device 156 has been sensed by the smart table106, the smart table 106 may then determine a necessary user input, atstep 1904. The determined necessary user input may be based on a bankingsession step being performed during a banking session. That is, thenecessary user input may depend on which point of a banking session theuser is in. For example, in some embodiments, the user may be at a pointin a banking session where they are asked to provide any of a variety ofinputs to perform a given action associated with the banking session.Accordingly, the necessary user input for the user to provide mayinclude general information (e.g., name, address, account information),a series of numbers (e.g., a deposit/withdrawal amount, a PIN), abiometric sample (e.g., a fingerprint, a facial recognition sample, aretinal scan), a signature (e.g., on a document or other form), or anyother necessary input for a given action during the banking session.Further, in some instances, the user may be at a point in a bankingsession where they are asked to weigh an object (e.g., a safety depositbox) using the tactile input device 156. Accordingly, the necessary userinput may also comprise placing the object onto the tactile input device156 to be weighed.

The smart table 106 may then determine the location of the tactile inputdevice 156 on the smart table 106, at step 1906. For example, in someembodiments, the tactile input device 156 may include pads 1302 arrangedon a base of the tactile input device 156 (e.g., as shown in FIG. 13).The pads 1302 may be configured to indicate to a touchscreen of thesmart table 106 the location and orientation of the base of the tactileinput device 156 (and thus the tactile input device 156) with respect tothe smart table 106. Although illustrated as protruding from the base ofthe tactile input device 156, it should be appreciated that, in someinstances, the pads 1302 may be incorporated into the base of thetactile input device 156, such that the pads 1302 sit flush with thesurface of the base of the tactile input device 156. In furtherembodiments, a camera or series of cameras above the smart table 106 maybe used to track the position of the tactile input device 156 andcommunicate said location with the smart table 106. In furtherembodiments, the smart table 106 may flash an indicator of where toplace the tactile input device 156. For example, the banking session mayrequire the tactile input device 156 to be moved between the customerand the branch employee. In this instance, the smart table 106 mayindicate a first area in front of the customer on the smart table 106 toplace the tactile input device 156 during a first step of a bankingsession. Then, as the banking session proceeds, the smart table 106 mayindicate a second area in front of the branch employee on the smarttable 106 to move the tactile input device 156.

In other embodiments, the tactile input device 156 may comprise an arrayof near-field communication (NFC) sensors that indicate to the smarttable 106 the location and orientation of the tactile input device 156.In some embodiments, multiple tactile input devices 156 may be placed onthe smart table 106 simultaneously, and the smart table 106 may beconfigured to pair with and determine the locations and orientations ofeach of the multiple tactile input devices 156. In some embodiments, thesmart table 106 may be configured to continuously determine the locationof the tactile input device 156 (or multiple tactile input devices 156).For example, in some instances, the tactile input device 156 may beutilized by multiple people during a banking session. Accordingly, thetactile input device 156 may be used and transferred between multiplepeople, and the smart table 106 may continuously determine or monitorthe location of the tactile input device 156 with respect to the smarttable 106.

The smart table 106 may then be configured to rearrange the userinterface based on the determined location of the tactile input device156 and/or the determined necessary user input, at step 1906. Forexample, the smart table 106 may rearrange the user interface togenerate the tactile input device area 1202 (or in some instancestactile input device areas 1202, if multiple tactile input devices 156are placed on the smart table 106) and the unobstructed area 1204 basedon the determined location(s) of the tactile input device(s) 156. Byrearranging the user interface, the smart table 106 may be configured toensure that user information is not obstructed by the tactile inputdevice(s) 156.

As described above, in some embodiments, the tactile input device 156may be configured to utilize the touch screen of the smart table 106.Accordingly, while rearranging the user interface, at step 1908, thesmart table 106 may also generate an appropriate touchscreen layoutunderneath the tactile input device 156, within the tactile input devicearea 1202, based on the determined necessary user input. Alternatively,in cases where the tactile input device 156 includes a touchscreen ofits own, the tactile input device 156 may be configured to prompt thesmart table 106 to not display anything within the tactile input devicearea 1202.

In some embodiments, instead of rearranging the user interface based onthe determined location of the tactile input device 156, the smart table106 may generate a predefined tactile input device area 1202 and apredefined unobstructed area 1204. In these instances, the predefinedtactile input device area 1202 may include a prompt for the user toplace the tactile input device 156 within the tactile input device area1202. This functionality may be used, for example, in instances wherethe location sensors are optionally omitted or ineffective, or whenparticular user interfaces are not able to be rearranged due to theircontent.

In any case, the smart table 106 may then communicate a necessary inputconfiguration to the tactile input device 156. The necessary inputconfiguration may be based on the determined necessary user input. Forexample, in one embodiment, the user may be at a point in a bankingsession where they are asked to enter general information such as a nameor address. In this instance, the necessary input configuration would bean alphanumeric configuration. In various other instances, the necessaryinput configuration may be various other types of configurations, suchas, for example, a numeric configuration, a signature configuration, abiometric configuration, a scale configuration, or any other necessaryinput configuration for a given action during a banking session. In someembodiments, the necessary input configuration may be determined basedon a field of focus in the banking session. For example, in someinstances, the customer may be prompted to enter identifying information(e.g., name, phone number, address) during a step of a banking session.In these instances, the field of focus may initially be a name entryarea where the customer may be presented with an alphanumeric layout.During another (e.g., a subsequent) step, the customer may be promptedto enter the customer's phone number. In this instances, the field offocus may be a phone number entry area where the customer may bepresented with a numeric input (e.g., 10-key).

Once the tactile input device 156 has received the necessary inputconfiguration from the smart table 106, the tactile input device 156 maybe configured to generate a tactile user interface having an appropriatelayout based on the necessary input configuration. For example, thetactile input device 156 may be configured to inflate appropriate inputareas using the key inflation device 1114 to generate inflatable keys1304 that are arranged to produce the tactile user interface having theappropriate layout based on the received necessary input configuration.Accordingly, the tactile user interface may be provided in the form ofany of the various layouts described above (e.g., the keyboard layout1400, the numeric keypad layout 1500, the authentication layout 1600,the signature box layout 1700, the scale layout 1800), a layout to allowthe user to zoom in or out on the smart table 106, or any other suitablelayout, as necessary for a given action during a banking session. Insome embodiments, the user may be able to select, on the smart table 106and/or the tactile input device 156, the desired layout independent ofthe necessary input. For example, during the banking session, the usermay desire a layout that allows the user to zoom in and out on the smarttable 106. In this instance, the user may be able to switch the layoutof the tactile input device 156 by selecting the desired layout on thesmart table 106 and/or the tactile input device 156.

Further, in some instances, the shape formed by the inflatable keys 1304may be based on user preference and/or may depend on size constraints ofthe tactile user interface corresponding to the necessary inputconfiguration. For example, in some instances, the keyboard layout 1400may have crescent shaped inflatable keys 1304. In some instances, thenumeric keypad layout 1500 may have round inflatable keys 1304.

Once the tactile user interface has been generated by the tactile inputdevice 156, the user may utilize the tactile input device 156 to providethe necessary user input, which the tactile input device 156 maycommunicate to the smart table 106, at step 1914. This communication maybe done instantaneously, thus allowing the entered information to bedisplayed on the smart table 106 as it is entered. In other embodiments,the information may be communicated only after a data entry has beenfinished (e.g., once the entire name or address has been entered) andsubmitted for transmission. In some embodiments, a data entry window maybe populated above the inflatable keys 1304 of the tactile input deviceto allow the user to track the entry on the tactile input device 156and/or the smart table 106. In some embodiments, the input may becommunicated via at least one of a network connection (e.g., Wi-Fi™), aBluetooth™ connection, a shared connection, or near-field communication(NFC). In some embodiments, the user input is communicated to the smarttable 106 and to the user device 104, and this communication can be donesimultaneously or near simultaneous. The user inputs communicated to theuser device 104 can be saved on the user device 104 for the user's ownrecords (e.g. so the user can later reference the information that theyinputted and provided to the provider).

In further embodiments, the display of the tactile input device 156 maybe configured to display UV lights to kill viruses. For example, thetactile input device 156 may receive an indication from the smart table106 that the banking session has been completed. In this instance, thedisplay of the tactile input device 156 may display UV lights for adetermined period of time (e.g., 30 seconds, 5 minutes, 20 minutes). Insome embodiments, the tactile input device 156 may be configured todisplay UV lights between inputs required by the branch employee and thecustomer.

The embodiments described herein have been described with reference todrawings. The drawings illustrate certain details of specificembodiments that provide the systems, methods and programs describedherein. However, describing the embodiments with drawings should not beconstrued as imposing on the disclosure any limitations that may bepresent in the drawings.

It should be understood that no claim element herein is to be construedunder the provisions of 35 U.S.C. § 112(f), unless the element isexpressly recited using the phrase “means for.”

As used herein, the term “circuitry” may include hardware structured toexecute the functions described herein. In some embodiments, eachrespective “circuit” may include machine-readable media for configuringthe hardware to execute the functions described herein. The circuit maybe embodied as one or more circuitry components including, but notlimited to, processing circuitry, network interfaces, peripheraldevices, input devices, output devices, sensors, etc. In someembodiments, a circuit may take the form of one or more analog circuits,electronic circuits (e.g., integrated circuits (IC), discrete circuits,system on a chip (SOCs) circuits, etc.), telecommunication circuits,hybrid circuits, and any other type of “circuit.” In this regard, the“circuit” may include any type of component for accomplishing orfacilitating achievement of the operations described herein. Forexample, a circuit as described herein may include one or moretransistors, logic gates (e.g., NAND, AND, NOR, OR, XOR, NOT, XNOR,etc.), resistors, multiplexers, registers, capacitors, inductors,diodes, wiring, and so on).

The “circuit” may also include one or more processors communicativelycoupled to one or more memory or memory devices. In this regard, the oneor more processors may execute instructions stored in the memory or mayexecute instructions otherwise accessible to the one or more processors.In some embodiments, the one or more processors may be embodied invarious ways. The one or more processors may be constructed in a mannersufficient to perform at least the operations described herein. In someembodiments, the one or more processors may be shared by multiplecircuits (e.g., circuit A and circuit B may comprise or otherwise sharethe same processor which, in some example embodiments, may executeinstructions stored, or otherwise accessed, via different areas ofmemory).

Alternatively or additionally, the one or more processors may bestructured to perform or otherwise execute certain operationsindependent of one or more co-processors. In other example embodiments,two or more processors may be coupled via a bus to enable independent,parallel, pipelined, or multi-threaded instruction execution. Eachprocessor may be provided as one or more general-purpose processors,application specific integrated circuits (ASICs), field programmablegate arrays (FPGAs), digital signal processors (DSPs), or other suitableelectronic data processing components structured to execute instructionsprovided by memory. The one or more processors may take the form of asingle core processor, multi-core processor (e.g., a dual coreprocessor, triple core processor, quad core processor, etc.),microprocessor, etc. In some embodiments, the one or more processors maybe external to the apparatus, for example the one or more processors maybe a remote processor (e.g., a cloud based processor). Alternatively oradditionally, the one or more processors may be internal and/or local tothe apparatus. In this regard, a given circuit or components thereof maybe disposed locally (e.g., as part of a local server, a local computingsystem, etc.) or remotely (e.g., as part of a remote server such as acloud based server). To that end, a “circuit” as described herein mayinclude components that are distributed across one or more locations.

Example systems and devices in various embodiments might include aprocessing unit, a system memory, and a system bus that couples varioussystem components including the system memory to the processing unit.Each memory device may include non-transient volatile storage media,non-volatile storage media, non-transitory storage media (e.g., one ormore volatile and/or non-volatile memories), etc. In some embodiments,the non-volatile media may take the form of ROM, flash memory (e.g.,flash memory such as NAND, 3D NAND, NOR, 3D NOR, etc.), EEPROM, MRAM,magnetic storage, hard discs, optical discs, etc. In other embodiments,the volatile storage media may take the form of RAM, TRAM, ZRAM, etc.Combinations of the above are also included within the scope ofmachine-readable media. In this regard, machine-executable instructionscomprise, for example, instructions and data which cause a generalpurpose computer, special purpose computer, or special purposeprocessing machines to perform a certain function or group of functions.Each respective memory device may be operable to maintain or otherwisestore information relating to the operations performed by one or moreassociated circuits, including processor instructions and related data(e.g., database components, object code components, script components,etc.), in accordance with the example embodiments described herein.

It should also be noted that the term “input devices,” as describedherein, may include any type of input device including, but not limitedto, a keyboard, a keypad, a mouse, joystick or other input devicesperforming a similar function. Comparatively, the term “output device,”as described herein, may include any type of output device including,but not limited to, a computer monitor, printer, facsimile machine, orother output devices performing a similar function.

Any foregoing references to currency or funds are intended to includefiat currencies, non-fiat currencies (e.g., precious metals), andmath-based currencies (often referred to as cryptocurrencies). Examplesof math-based currencies include Bitcoin, Litecoin, Dogecoin, and thelike.

It should be noted that although the diagrams herein may show a specificorder and composition of method steps, it is understood that the orderof these steps may differ from what is depicted. For example, two ormore steps may be performed concurrently or with partial concurrence.Also, some method steps that are performed as discrete steps may becombined, steps being performed as a combined step may be separated intodiscrete steps, the sequence of certain processes may be reversed orotherwise varied, and the nature or number of discrete processes may bealtered or varied. The order or sequence of any element or apparatus maybe varied or substituted according to alternative embodiments.Accordingly, all such modifications are intended to be included withinthe scope of the present disclosure as defined in the appended claims.Such variations will depend on the machine-readable media and hardwaresystems chosen and on designer choice. It is understood that all suchvariations are within the scope of the disclosure. Likewise, softwareand web implementations of the present disclosure may be accomplishedwith standard programming techniques with rule based logic and otherlogic to accomplish the various database searching steps, correlationsteps, comparison steps and decision steps.

The foregoing description of embodiments has been presented for purposesof illustration and description. It is not intended to be exhaustive orto limit the disclosure to the precise form disclosed, and modificationsand variations are possible in light of the above teachings or may beacquired from this disclosure. The embodiments were chosen and describedin order to explain the principals of the disclosure and its practicalapplication to enable one skilled in the art to utilize the variousembodiments and with various modifications as are suited to theparticular use contemplated. Other substitutions, modifications, changesand omissions may be made in the design, operating conditions andarrangement of the embodiments without departing from the scope of thepresent disclosure as expressed in the appended claims.

What is claimed is:
 1. A tactile user input system comprising: a tactileinput device; and a smart table comprising a display screen, a networkinterface and a processing circuit, the network interface structured tofacilitate data communication with the tactile input device via anetwork, the processing circuit comprising a processor and a memory, theprocessing circuit structured to: determine a placement of the tactileinput device on the smart table; determine a necessary user input;determine a location of the tactile input device on the smart table;rearrange a user interface of the smart table based on at least one ofthe necessary user input or the location of the tactile input device onthe smart table; and communicate a necessary input configuration to thetactile input device to be used by the tactile input device to generatea tactile user interface on the tactile input device having a layoutconfigured to receive the necessary user input; wherein the tactileinput device is configured to be used to remotely provide authorizationfor a transaction made using the smart table.
 2. The system of claim 1,wherein the layout comprises at least one of: an alphanumeric keyboardlayout configured to allow a user to provide alphanumeric information; anumeric keyboard layout configured to allow the user to provide numericinformation; an authentication layout configured to allow the user toprovide a biometric sample; a signature layout configured to allow theuser to provide a signature; or a scale layout configured to allow theuser to weigh an object.
 3. The system of claim 1, wherein theprocessing circuit is configured to determine the placement of thetactile input device on the smart table using at least one of aBluetooth device or a near-field communication (NFC) device.
 4. Thesystem of claim 1, wherein the display screen comprises a touchscreen,wherein the processing circuit is configured to determine the locationof the tactile input device based on the touchscreen of the smart tablerecognizing a base of the tactile input device.
 5. The system of claim1, wherein the tactile input device is configured to be paired with thesmart table via at least one of a network connection, a Bluetoothconnection, a shared connection, or a near-field communication (NFC)connection.
 6. The system of claim 1, wherein the tactile input deviceis configured to receive user input, wherein the user input comprises atleast one of an alphanumeric input, a numeric input, a signature input,a biometric input, or a weight input.
 7. The system of claim 1, whereinthe determined necessary user input is determined based on a userselection made during a banking session.
 8. The system of claim 1,wherein the tactile input device is functionally independent of thesmart table.
 9. A tactile input device comprising: a touch screen; atactile overlay including a plurality of selectable keys and configuredto selectively generate a plurality of tactile user interfaces, each ofthe plurality of tactile user interfaces having a unique layout; aprocessing circuit configured to: receive a necessary inputconfiguration from a smart table, wherein the smart table comprises adisplay screen; generate a tactile user interface on the touch screenhaving a layout based on the necessary input configuration; receive, viathe tactile user interface, a user input; and communicate the user inputto the smart table, wherein the user input comprises an authorizationfor a transaction made using the smart table, wherein the user input iscommunicated to the smart table when the tactile input device is remotefrom the smart table.
 10. The tactile input device of claim 9, furthercomprising: a weight sensor configured to weigh an object placed on thetactile input device.
 11. The tactile input device of claim 9, whereinthe layout comprises at least one of: an alphanumeric keyboard layoutconfigured to allow a user to provide alphanumeric information; anumeric keyboard layout configured to allow the user to provide numericinformation; an authentication layout configured to allow the user toprovide a biometric sample; a signature layout configured to allow theuser to provide a signature; or a scale layout configured to allow theuser to weigh an object.
 12. The tactile input device of claim 11,wherein the tactile user interface comprises the authentication layout,wherein the authentication layout comprises: a 10-key PIN layout; and abiometric scanner.
 13. The tactile input device of claim 9, wherein theprocessing circuit is configured to communicate the necessary inputconfiguration to the smart table via at least one of a networkconnection, a Bluetooth connection, a shared connection, or near-fieldcommunication (NFC).
 14. The tactile input device of claim 9, whereinthe touch screen is configured to display UV lights after a usersession, the UV lights configured to sanitize the touch screen.
 15. Atactile input device comprising: a tactile overlay including a pluralityof selectively inflatable keys and configured to selectively generate aplurality of tactile user interfaces, each of the plurality of tactileuser interfaces having a unique layout; and a processing circuitconfigured to: receive a necessary input configuration from a smarttable, wherein the smart table comprises a display screen; generate atactile user interface having a layout based on the necessary inputconfiguration by selectively inflating at least one of the plurality ofselectively inflatable keys; and receive a user input via the tactileuser interface, wherein the user input comprises an authorization for atransaction made using the smart table, wherein the user input iscommunicated to the smart table when the tactile input device is remotefrom the smart table.
 16. The tactile input device of claim 15, furthercomprising: a weight sensor configured to weigh an object placed on thetactile input device.
 17. The tactile input device of claim 15, whereinthe layout comprises at least one of: an alphanumeric keyboard layoutconfigured to allow a user to provide alphanumeric information; anumeric keyboard layout configured to allow the user to provide numericinformation; an authentication layout configured to allow the user toprovide a biometric sample; a signature layout configured to allow theuser to provide a signature; or a scale layout configured to allow theuser to weigh an object.
 18. The tactile input device of claim 17,wherein the authentication layout comprises: a 10-key PIN layout; and abiometric scanner.
 19. The tactile input device of claim 15, wherein thetactile input device is configured to be paired with the smart table viaat least one of a network connection, a Bluetooth connection, a sharedconnection, or near-field communication (NFC).